Add reload_secure_settings node object properties #5825
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
pquentin
approved these changes
Dec 10, 2025
Member
pquentin
left a comment
pquentin
left a comment
There was a problem hiding this comment.
Thanks! That's perfect. LGTM.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds schema entries for the following properties in the reload-secure-settings response.
secure_setting_names: JSON array of secure setting names from ES keystorekeystore_path: JSON string with file system path to keystore filekeystore_digest: JSON string with hex-encoded SHA-256 hash of keystore file raw byteskeystore_last_modified_time: JSON string with ES keystore last-modified date-timeThese changes will be available starting in ES 9.3.0.
It is related to the following:
Issue: elastic/elasticsearch#112268
PR: elastic/elasticsearch#138052